The ATCommandListener interface implements callback functions for:
The user must create an implementation class for ATCommandListener to receive AT events. The
ATEvent method of this class must contain the processing code for the different AT-Events (URCs). The
RINGChanged, DCDChanged, DSRChanged and
CONNChanged methods should contain the processing code for possible state changes. This code shall leave the listener context as soon as possible (i.e. running a new thread). While the callback method does not return it cannot be called again if changes occur.
The CONNChanged method indicates the start and the end of data connections. During a data connection it is possible to transfer data with the I/O stream methods (see
Section 13.1.1.3). Some data services (i.e. FTP) transfer the data so quickly, that the
CONNChanged start and close events are received even parallel to the response of the AT command which originated the data connection. The user’s application must realize, that the data connection had taken place and read the data with the I/O stream read methods afterwards.
An ATEvent or a URC is a report message sent from the module to the application. An unsolicited result code is either delivered automatically when an event occurs or as a result of a query the module previously received. However, a URC is not issued as a
direct response to an executed AT command. Some URCs must be activated with an AT command.
After creating an instance of the ATCommandListener class, it must be passed as a parameter to the
ATCommand.addListener() method. The callback methods of the instance will be called by the runtime system each time the corresponding events (URCs or signal state changes) occur on the corresponding device AT parser.
The ATCommand.removeListener() method removes a listener object that has been previously added to the internal list table of listener objects. After it has been removed from the list it will not be called when URCs occur. If it was not previously registered the list remains unchanged.